Ekahau RTLS Controller API Reference

Welcome to Ekahau RTLS Controller API Reference.

These pages document the Ekahau RTLS Controller 5 web service API.

See the Developer Guide of the API. Or take the quick route: List positions of 20 most recent tags.

Services

/epe/pos - position

Main API: Query tag positions, from database or in real-time.

/epe/eve - event rules, stream and history

Event service: Events are generated by rules and output to streams and a history record.

/epe/edp - edp messages, stream and history

Edp service: EDP messages received from tags and output to streams and a history record.

/epe/status - status stream and history

Status service: Query status change events, from database or in real-time.

/epe/route - route control, stream, history, and navigation

Route service: Route service provides information about tag routes.

/epe/sensor - sensor data stream and history

Sensor service: Query sensor data, from database or in real-time.

/epe/msg - tag menu, messages

Tag control: Tag menu and message API.

/epe/cfg - tag configuration

Tag control: Groups, configurations, commands, firmware files.

/epe/asset - asset management and binding

Asset service: Create and delete assets, and modify bindings.

/epe/mod - model

Model service: Uploading and downloading positioning models created with Ekahau Site Survey.

/epe/map - map

Map image service: Renders map images with tag positions.

/epe/sys - system

System service: User management, system configuration, status, logs, licensing.

/epe/tftp - tftp server

TFTP-server: Delivers firmware files for T301.

/epe/eng - engine

Positioning Engine: The core positioning algorithm.

/epe/tag - tag

Tag maintenance: HTTP/ASCII protocol for T201. EMP UDP protocol for T301.

/epe/rec - receiver

Signal receiver: YAX2 UDP&TCP protocol for T201. ELP UDP protocol for T301.

/epe/aprec - access point rssi receiver

Signal receiver: Receive RSSI signals from access points and controllers.

/epe/test - test

Test service: Test HTTP communication and code of the client application in various tricky situations. These commands can be safely used; they don't manipulate RTLS Controller databases.